Process Enablement in Network Downtime Condition

ABSTRACT

A computer implemented method of enabling a mobile device connected to a network that includes establishing a connection with the peripheral device when the mobile device fails to connect to the network; transmitting a document to the peripheral device for processing; receiving the processed document from the peripheral device; storing the processed document in a memory of the mobile device; and sending the processed document to a remote storage location once the mobile device is determined to be actively communication with the network.

CROSS REFERENCES TO RELATED APPLICATIONS

This patent application is related to U.S. patent application Ser. No. 13/731,644, filed Dec. 31, 2012, entitled “Process Enablement in Network Downtime Condition and U.S. patent application Ser. No. 14/135,760, entitled “Process Enablement in Network Downtime Condition”, which was filed on Dec. 20, 2013, both of which are assigned to the assignee of the present application.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

None.

REFERENCE TO SEQUENTIAL LISTING, ETC

None.

BACKGROUND

1. Technical Field

The present disclosure relates generally to a method for enabling processes of a device and, more specifically, enabling processes of a device during a network downtime condition.

2. Description of the Related Art

In many environments that rely on electronic and paper-based processes, there is a reliance on a network infrastructure to effectively and efficiently perform process-oriented work tasks. If the network infrastructure becomes unavailable (i.e., a network downtime condition occurs) through planned or unplanned network outages, the access to critical process elements and steps may also become unavailable. Examples of network-based process elements or steps include, but are not limited to, accessing centrally located documents and forms (such as on a server or in a remote storage location), processing workflow steps (such as scanning documents to an electronic file share) and completing field entries in forms utilizing electronically stored data.

In many cases, once the network becomes unavailable, workers shift from electronic process entry to a more manual process, such as paper-based processing. The manual processing of forms and documents may lead to a higher potential for error and a less efficient processing of documents. Additional labor may also be needed once the network is back up or running in order to process the data that was manually captured on paper during the network downtime condition.

Thus, there is a need for a solution that will enable a device to continue utilizing network-based processes during network downtime (i.e., where communication with a network is unavailable). There is also a need for a solution that will maintain efficient and accurate processing of documents with minimal procedural or process changes when a network infrastructure is unavailable.

SUMMARY

A system and methods of enabling a mobile device when the mobile device fails to connect with the network are disclosed herein. One example embodiment of enabling the mobile device may include activating an ad-hoc network connection with a peripheral device when the mobile device fails to connect to the network. The mobile device may then transmit a document to the peripheral device for processing and receive the document from the peripheral device. The received document may be further processed by the mobile device and/or may be stored in a queue until the mobile device is determined to be in active communication with the network.

In one aspect of the example embodiment, processing of the document may include automatically filling the document with information. In an aspect of the example embodiment, the information may be retrieved from scanning a barcode.

In another aspect of the example embodiment, the connection established with the peripheral device may be an ad-hoc network connection. In one aspect, the connection between the mobile device and the peripheral device may be established when the mobile device is within close proximity to the peripheral device. In another aspect, the connection may be established using a wireless radio.

From the foregoing disclosure and the following detailed description of various example embodiments, it will be apparent to those skilled in the art that the present disclosure provides a significant advance in the art of methods for enabling network-based processes in a device during a network downtime condition. Additional features and advantages of various example embodiments will be better understood in view of the detailed description provided below.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned and other features and advantages of the present disclosure, and the manner of attaining them, will become more apparent and will be better understood by reference to the following description of example embodiments taken in conjunction with the accompanying drawings. Like reference numerals are used to indicate the same element throughout the specification.

FIG. 1 is one example embodiment of a networked system.

FIG. 2 is a flowchart of one example method for enabling a device of the system of FIG. 1 to perform network-based document processing during a network downtime condition.

DETAILED DESCRIPTION OF THE DRAWINGS

It is to be understood that the disclosure is not limited to the details of construction and the arrangement of components set forth in the following description or illustrated in the drawings. The disclosure is capable of other example embodiments and of being practiced or of being carried out in various ways. For example, other example embodiments may incorporate structural, chronological, process, and other changes. Examples merely typify possible variations. Individual components and functions are optional unless explicitly required, and the sequence of operations may vary. Portions and features of some example embodiments may be included in or substituted for those of others. The scope of the disclosure encompasses the appended claims and all available equivalents. The following description is, therefore, not to be taken in a limited sense, and the scope of the present disclosure is defined by the appended claims.

Also, it is to be understood that the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use herein of “including,” “comprising,” or “having” and variations thereof is meant to encompass the items listed thereafter and equivalents thereof as well as additional items. Further, the use of the terms “a” and an herein do not denote a limitation of quantity but rather denote the presence of at least one of the referenced item.

In addition, it should be understood that example embodiments of the disclosure include both hardware and electronic components or modules that, for purposes of discussion, may be illustrated and described as if the majority of the components were implemented solely in hardware.

It will be further understood that each block of the diagrams, and combinations of blocks in the diagrams, respectively, may be implemented by computer program instructions. These computer program instructions may be loaded onto a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus may create means for implementing the functionality of each block or combinations of blocks in the diagrams discussed in detail in the description below.

These computer program instructions may also be stored in a non-transitory computer-readable medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium may produce an article of manufacture, including an instruction means that implements the function specified in the block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus implement the functions specified in the block or blocks.

Accordingly, blocks of the diagrams support combinations of means for performing the specified functions, combinations of steps for performing the specified functions and program instruction means for performing the specified functions. It will also be understood that each block of the diagrams, and combinations of blocks in the diagrams, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and computer instructions.

Disclosed are a system and methods for enabling network-based processing by a mobile device connected to a network during a period of an inactive communication with the network. According to one example embodiment of the present disclosure, when the mobile device is detected to be inactively connected to the network such as, for example, during a network downtime, the mobile device may activate an ad-hoc network connection with a peripheral device. The mobile device may then send the document to be processed to the peripheral device. In one example embodiment, the peripheral device may perform the network-based process on the document such as, for example, inputting or completing information on the document. Upon completion of the network-based processing of the document by the peripheral device, the processed document may be sent to the mobile device for further processing and/or storing into a queue until the computing device is determined to be in an active communication with the network.

The system and methods described herein may enable workflow solutions to continue with minimal procedural or process changes when the network infrastructure is unavailable either through a planned or unplanned network outage or when the computing device loses its communication with the network. The example embodiments described herein may be achieved by utilizing storage and ad-hoc networking capabilities along with forms server logic on a computing device or appliance.

FIG. 1 is one example embodiment of a networked system 100, according to one example embodiment of the present disclosure. System 100 is a data communication system that may include a mobile device 105, a remote computer 110 and a peripheral device, such as multi-function printing device (MFP), 115. Remote computer 110 and MFP 115 may be connected through a network 120.

Mobile device 105 may be any computing device that is portable, handheld or pocket-sized such as, for example, a mobile device (e.g., a cell phone), a smart phone, a handheld computer, a personal digital assistant (PDA), a notebook computer, a tablet computer, or any other remote computing device, such as a special-purpose remote computing device (e.g., e-book reader). Mobile device 105 may include a display unit, an input device (e.g., keyboard), a processor, and memory, such as RAM, ROM, and/or NVRAM. Mobile device 105 may include an imaging driver (not shown) that may communicate with MFP 115 via a communications link. In addition, the imaging driver may provide processed documents for storing and/or printing by MFP 115.

Additionally, mobile device 105 may include at least one control unit such as, for example, a processor (not shown) that controls the operation of the mobile device. The control unit of mobile device 105 may include one or more embedded solutions that may store and provide templates or copies of one or more documents for use by a user of MFP 115 or mobile device 105.

Mobile device 105 may store in its memory one or more electronic documents that may serve as local copies of forms or templates which a user of mobile device 105 may use for data input and/or processing. For example, in the healthcare industry, the forms or templates may include, but are not limited to, patient intake forms, patient records, medical history forms, reporting and billing forms, and other types of documents. The local copies of the forms or templates may be stored in the memory of mobile device 105, such that when a user of mobile devices wishes to access the form to be filled in with information, the user may simply operate mobile device 105 to retrieve a copy of the form or template from its memory and print a hard copy. Having local copies of the electronic forms allows the form templates to be readily available for use as desired or needed, thus eliminating the need for mobile device 105 to connect to a remote storage server every time a user of mobile device 105 wishes to use a copy of the one or more form templates available in the memory of mobile device 105.

In another example embodiment, mobile device 105 may be, for example, a personal or desktop computer. Mobile device 105 may include a display unit, an input device (e.g., keyboard), a processor, and memory, such as RAM, ROM, and/or NVRAM. Mobile device 105 may also include a mass data storage device, such as a hard drive, CD-ROM and/or DVD units. Mobile device 105 may include an imaging driver (not shown) that may communicate with MFP 115 via a communications link. In addition, the imaging driver may provide processed documents for storing and/or printing by MFP 115.

MFP 115 may be network-enabled and capable of communicating with remote computer 110. For example, MFP 115 may be connected to remote computer 110 via a communication link, which may be established by a wired or wireless connection such as, for example, an Ethernet connection. MFP 115 may be any device capable of printing or producing a hard copy data file or document stored in electronic form, such as a laser, inkjet or dot matrix printer or a multi-function printing device capable of performing other functions, such a faxing, e-mailing, scanning and/or copying, in addition to printing.

MFP 115 may include a control unit and a print engine. The control unit of MFP 115 may include one or more embedded solutions that may store and provide templates or copies of one or more documents for use by a user of MFP 115 or mobile device 105. In some example embodiments, the embedded solution may be a software application that may be stored in a non-transitory computer readable storage medium associated with the control unit and may be executed by the control unit in accordance with programmed logic associated with the software application. During operation, MFP 115 may include in its memory a software program including program instructions that function as a document processing application for processing one or more documents received from mobile device 105.

In one aspect, MFP 115 may include a processor (not shown) in communication with a user interface (not shown), a memory (not shown), and a scanning subsystem (not shown). The user interface may be a graphical user interface, a monitor, a series of buttons, a touch-sensitive display panel, a text interface such as a 2-line display, and a voice-activated interface or the like. In one aspect, the user interface may serve as an operating panel for MFP 115. It is also within the scope of this aspect to utilize a computer (not shown), such as personal computer, having a monitor as the user interface. Those skilled in the art will appreciate that MFP 115 may include various additional components, such as a facsimile, scanner and/or card reader. MFP 115 may also include one or more appropriate software applications configured to receive print data or one or more files from a print server (not shown) and to output or print pages through a print engine (not shown) of MFP 115.

MFP 115 may be connected to network 120 by a direct cable or optical connection or by a network connection such as, for example, an Ethernet local area network (LAN). The connection between MFP 115 and network 120 may be established by an Internet connection, or via a wide area network (WAN). Communication links between MFP 115 and network 120 may be established by using standard electrical cabling or bus structures. The communication links may also be established using wireless connections. Where the communication links are wireless, MFP 115 may further include a radio transceiver. The wireless connection may be, for example, 2G, 3G, Bluetooth, CDMA, DECT, TDMA, UMTS-TDD, WiBro, WiFi, or WiMAX. Wired connections may be proprietary or constructed in accordance with a communications industry standard, such as USB or FireWire (IEEE-1394).

When used in a LAN networking environment, MFP 115 may be connected to the local area network through a network interface or adapter. When used in a WAN networking environment, MFP 115 may include a modem, T1 line, satellite or other means for establishing communications over a wide area network, such as the Internet. The modem, which may be internal or external, may be connected to a system bus of MFP 115 via a serial port interface.

In a networked environment, program modules, applications or workflow solutions, or portions thereof, performed by MFP 115 may be stored in local or remote memory storage devices. In some example embodiments, MFP 115 may be linked to other processing devices in order to perform certain tasks. It will be appreciated that the network connections described are illustrative and other means of establishing a communications link between the computing devices may be used.

MFP 115 may store in its memory one or more electronic documents that may serve as local copies of forms or templates which a user of MFP 115 may use for data input and/or processing. For example, in the healthcare industry, the forms or templates may include, but are not limited to, patient intake forms, patient records, medical history forms, reporting and billing forms, and other types of documents. The local copies of the forms or templates may be stored in the memory of MFP 115, such that when a user of MFP 115 wishes to print a copy of the form to be filled in with information, the user may simply operate the MFP 115 to retrieve a copy of the form or template from its memory and print a hard copy. Having local copies of the electronic forms allows the form templates to be readily available for use as desired or needed, thus eliminating the need for MFP 115 to connect to a remote storage server every time a user of MFP 115 wishes to use a copy of the one or more form templates available in the memory of MFP 115. MFP 115 may also store in its memory completed forms or templates scanned in by a user.

In some example embodiments, MFP 115 may be capable of processing forms or templates without user intervention. For example, MFP 115 may contain computer program instructions or an application for automatically receiving and converting a received document from one format to a different format without user intervention. In yet other example embodiments, MFP 115 may contain computer program instructions or an application for automatically receiving a document, recognizing document type, classifying the document, extracting certain data from the document, and/or appending metadata to the document.

During use, MFP 115 may operate in a networked environment using logical connections to one or more other computing configurations, such as remote computer 110. Remote computer 110 may be a personal computer, a server, a router, a network PC, a peer device or other common network node. As set forth above, the logical connections between MFP 115 and remote computer 110 may include a local area network (LAN) and/or a wide area network (WAN).

In one example embodiment, remote computer 110 may be a central capture or repository service that may be used to store electronic documents containing information gathered using MFP 115. For example, remote computer 110 may be a centralized document management system such as, for example, a Health Information Management System (HIMS).

In one example embodiment, remote computer 110 may provide updated versions of the local copies of the electronic form documents or templates stored in MFP 115. For example, when the local copies of the form templates are updated with a new version, remote computer 110 may provide MFP 115 with the newer versions of the form templates through an update.

Updating the local copies of the form templates in MFP 115 may include automatically delivering updated copies to MFP 115. Automatic delivery of updated copies may be performed by either a pull method or a push method. In the pull method, MFP 115 may periodically poll the remote computer 110 to ensure it has the most recent versions of the forms in its memory. In another example embodiment, a central forms server may store the form templates, and MFP 115 may periodically poll the central forms server for updated copies of form templates.

In the push method, MFP 115 may use subscription services such as, for example, Really Simple Syndication (RSS), in order to be notified when updates are available and/or when an action is required to update the local copies of the form templates. A means to register MFP 115 for syndication services may be utilized to ensure correct and current forms are available on MFP 115. Syndication services for subscribing to updates as described herein is illustrative and should not be considered limiting. Other subscription services as will be known in the art may be used in some alternative example embodiments.

Mobile device 105 and MFP 115 may connect and communicate wirelessly through short-range, ad hoc networks, which may be established dynamically and automatically as the Mobile device 105 and MFP 115 enter and leave radio proximity to each other.

With continued reference to FIG. 1, network 120 may be any network, communications network, or network/communications network system such as, but not limited to, a peer-to-peer network, a hybrid peer-to-peer network, a Local Area Network (LAN), a Wide Area Network (WAN), a public network, such as the Internet, a private network, a cellular network, a combination of different network types, or other wireless, wired, and/or a wireless and wired combination network capable of allowing communication between two or more computing systems, as discussed herein. Other types of networks and communications mode may be used to connect mobile device 105, MFP 115 and remote computer 110 from each other, as will be known in the art.

Although the system in FIG. 1 shows only one mobile device 105, one MFP 115 and one remote computer 110, networked system 100 may have any number of components and devices, as will be appreciated by one of ordinary skill in the art.

FIG. 2 is a flowchart of one example method 200 for enabling a device, such as MFP 115 of networked system 100, to perform network-based document processing during a network downtime condition or communications loss between the device and remote computer 110. Method 200 may enable workflow solutions to continue with minimal procedural or process changes during such outages.

Method 200 may include determining if the mobile device 105 is actively connected to network 120, activating an ad-hoc network connection with a MFP 115, sending a document to the MFP 115 for processing, returning the processed document to mobile device 105, and storing the document in a memory of the mobile device 105 for transmission to a remote computer when network 120 is determined to be in an uptime condition or communication is re-established between the mobile device 105 and network 120. Allowing ad-hoc network connections to be established between mobile device 105 MFP 115 enables electronic transfer of a downtime document for processing by MFP 115. This transfer enables electronic capture of data into the document for a higher efficiency and success rate of processing information. Availability of the electronic downtime form may also minimize the changes in process and procedure regardless of network state.

With reference to FIG. 2, at block 205, it is determined whether mobile device 105 is actively connected or communicating with network 120. An active connection with network 120 may refer to a state wherein mobile device 105 is able to communicate with a node in network 120 that is connected to mobile device 105 such as, for example, remote computer 110.

In one example aspect, determining if mobile device 105 is in active connection or communication with network 120 may include determining whether network 120 is in an uptime or downtime condition. A network uptime condition may refer to a period during which network 120 is operational, and mobile device 105 is able to communicate with other nodes in network 120. A network downtime condition may refer to a period during which network 120 is determined to not be operational, and communication with other nodes in network 120 is unavailable. A network downtime condition may occur during planned outages such as, for example, during routine maintenance Network downtime condition may also occur during unplanned outages caused by unexpected factors such as, for example, communication and system failures. Other factors that may cause network downtime condition will be apparent to one of ordinary skill in the art.

In another example aspect, determining if mobile device 105 is in active connection or communication with network 120 may include determining whether mobile device 105 is able to connect or communicate with the device needed to perform the network-based processing. For example, if the form templates are stored on remote computer 110 and the network-based processing is the downloading of forms to mobile device 105, mobile device 105 is in active communication with network 120 when mobile device 105 is able to communicate with remote computer 110 and receive the forms.

A means to detect a network downtime condition may be incorporated in mobile device 105 such as, for example, an attempt to contact remote computer 110. The attempt to contact remote computer 110 may return a positive or negative feedback. In some example embodiments, positive feedback may indicate a successful communication link between mobile device and remote computer 110 and vice-versa while negative feedback may indicate an unsuccessful or failed communication between mobile device 105 and remote computer 110. At block 210, if mobile device 105 is determined to be in an inactive connection to network 120 indicating a network downtime condition or failure to communicate with remote computer 110, a means for establishing ad-hoc network connection may be activated in mobile device 105 to connect to MFP 115 by coming in proximity to MFP 115 and searching for an ad-hoc network connection. Ad-hoc network connection may refer to a feature of the IEEE 802.11 standard. The ad hoc communications mode allows the radio network interface card (NIC) of MFP 115 to operate in what the IEEE 802.11 standard refers to as an independent basic service set (IBSS) network configuration. In an IBSS configuration, devices may communicate directly with each other without an intermediary, e.g., without an access point device.

MFP 115 may include a wireless radio to allow for proximity ad-hoc connections. In some example embodiments, other means for establishing a connection between MFP 115 and client device 105 may be performed by using proximity-based protocols such as, for example, wireless USB and NFC. In yet other example embodiments, other means for connecting MFP 115 to client device 105 may be used, as will be known in the art.

At block 215, after MFP 115 and mobile device 105 have successfully established a connection or communications link, mobile device 105 may send a document to MFP 115. For example, mobile device 105 may send to MFP 115 a template or a blank form that may be filled in or completed with information or data either automatically by MFP 115 or manually by a user of MFP 115. In one example embodiment the user could interact with the operator panel of the MFP 115 to enter information in the document. Example information for a healthcare template or form may include, for example, a patient's personal data (e.g., name, address, marital status, etc.), the date, the time, diagnosis, etc. It will be appreciated by those skilled in the art that other information or data may be used to complete templates or forms used in other industries.

At block 220, the document or template may be processed by MFP 115. In one example embodiment, processing the document may include populating the form with relevant information received from a user. For example, the user of MFP 115 may process a form received from mobile device 105 by populating or inputting data into the fields in the form with information that is relevant to the form such as, for example, a patient's personal information.

In another example embodiment, processing the document may include capturing a barcode and retrieving information from the barcode to populate the document. Capturing the barcode may include taking an image of the barcode using a camera, a barcode scanner or any image-capturing and/or information-retrieving component included in MFP 115. For example, in a healthcare scenario, a healthcare worker may download a form from mobile device 105 to MFP 115; select a specific process or workflow by launching an information-retrieving application, such as a barcode scanning application; and capture a patient's barcode (e.g., from a chart). An application in MFP 115 may automatically fill in or complete the proper fields on the form using the retrieved information from the barcode. When information is retrieved from a barcode, the need for manual user input may be eliminated, or at least reduced.

Upon retrieving information from the barcode, fields in the document may be automatically completed or filled in with the retrieved information. Filling in the fields in the document may include utilizing forms logic to fill in the correct fields with the retrieved barcode information (e.g., filling in the patient name in the field corresponding to the patient name, filling in the patient number in the field corresponding to the patient number, etc.). In some example aspects, filling in the fields may also involve process steps such as, for example, recording a measurement such as patient temperature and/or marking the process as completed along with recording a timestamp. In other example aspects, steps may also include filling in contextual information such as time, date, location, and/or identification of the clinician performing the process steps, etc.

At block 225, MFP 115 may send or transmit the processed document to mobile device 105, and mobile device 105 may store the processed document in its memory. In one aspect, storing the processed document may include adding the document to a queue of one or more processed documents to be automatically sent to remote computer 110 for storage once mobile device 105 is determined to be in active communication with network 120 and remote computer 110. For example, the electronic form completed in MFP 115 may be sent to mobile device 105 for submission into remote computer 110. In another aspect, mobile device 105 may check for an uptime condition of network 120 and/or active connection with remote computer 110 while storing the processed document in its memory, and when mobile device 105 is determined to be in active connection with remote computer 110, mobile device 105 may submit the completed electronic form to remote computer 110 for storage.

In another aspect, storing the processed document may include adding the document to a queue of one or more processed documents to be sent to a centralized document management system or central storage repository for storage once mobile device 105 is determined to be in active communication with network 120. For example, the electronic form completed in MFP 115 may be sent to mobile device 105 for submission into the centralized document management system for storage once communication with network 120 is re-established.

In some example alternative embodiments, mobile device 105 may store the processed document in its memory until an active communication with network 120 is detected, and the remote computer 110 or central storage repository requests transmission of the processed documents for storing.

It will be understood that the example applications described herein are illustrative and should not be considered limiting. It will be appreciated that the actions described and shown in the example flowcharts may be carried out or performed in any suitable order. It will also be appreciated that not all of the actions described in FIG. 1 need to be performed in accordance with the embodiments of the disclosure and/or additional actions may be performed in accordance with other embodiments of the disclosure.

Many modifications and other example embodiments of the disclosure set forth herein will come to mind to one skilled in the art to which these disclosure pertain having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation. 

What is claimed is:
 1. A method of enabling a mobile device connected to a network, comprising: activating an ad-hoc network connection with a peripheral device when the mobile device fails to connect to the network; transmitting a document to the peripheral device for processing; receiving the processed document from the peripheral device; storing the processed document in a memory of the mobile device; and sending the processed document to a remote storage location once the mobile device is determined to be actively communicating with the network.
 2. The method of claim 1, wherein the mobile device receives a request for the processed document prior to the sending.
 3. The method of claim 1, wherein the mobile device automatically performs the sending the processed document to the remote storage location once the mobile device is determined to be actively communicating with the network.
 4. The method of claim 1, further comprising receiving an updated copy of the document from the remote storage server.
 5. The method of claim 1, wherein the processing includes capturing barcode information.
 6. The method of claim 1, wherein the storing the processed document includes adding the processed document to a queue of one or more documents stored in the memory.
 7. The method of claim 6, further comprising sending the one or more documents in the queue to the remote storage server once the mobile device is determined to be actively communicating with the network.
 8. A peripheral device with a non-transitory computer-readable storage medium containing computer executable instructions to: establish a connection with the mobile device, receiving a document from the mobile device; processes the document; transmit the processed document to the mobile device, wherein the connection with the peripheral device is established when the mobile device fails to communicate with a network.
 9. The peripheral device of claim 8, wherein the connection established with the mobile device is an ad-hoc network connection.
 10. The peripheral device of claim 9, wherein the establishing the ad-hoc network connection includes connecting to the peripheral device using a wireless radio in the mobile device.
 11. The peripheral device of claim 9, wherein the establishing the ad-hoc network connection includes connecting to the peripheral device using one or more proximity-based protocols.
 12. The peripheral device of claim 8, wherein the processing the document includes converting the document from a first format to a second format.
 13. The peripheral device of claim 8, wherein the processing the document includes at least one of recognizing document type, classifying the document, extracting certain data from the document, and appending metadata to the document.
 14. A method of enabling form processing of a mobile device connected to a network, comprising: automatically determining if the network has returned to operation; if the network has not returned to the operation, activating an ad-hoc network connection with the peripheral device; sending a form to the peripheral device for population of fields; receiving the populated form from the peripheral device; storing the populated form in a memory of the mobile device until the network is determined to have returned to the operation and sending the stored populated form to a remote storage location once the network is determined to have returned to the operation.
 15. The method of claim 14, further comprising storing a copy of the form in the memory of the mobile device.
 16. The method of claim 14, further comprising receiving an updated master form from the remote storage location.
 17. The method of claim 14, further comprising periodically polling a remote storage server to check for an updated form.
 18. The method of claim 14, wherein the sending the stored populated form automatically occurs once the network is determined to have returned to the operation.
 19. The method of claim 14, wherein the activating the ad-hoc network connection includes connecting with the peripheral device using a wireless radio.
 20. The method of claim 14, wherein the activating the network connection includes connecting with the peripheral device using a proximity-based protocol. 